Global Navigation is the list of navigation links your users find in the Header on every page in Salesforce. Your Global Navigation includes a Navigation Bar where your users find the App Launcher, App Name, and Pages that each App includes.
Navigation BarDesktop Only
About Global Navigation
1.0. Building the Navigation Bar
The navigation bar is composed of a wrapper and 2 required regions:
- Primary, which contains the App Launcher and App Name
- Secondary, which contains the App Items, for navigating within the current app
The markup should follow the order listed above for proper keyboard interaction set by the 508 compliance standards. Each included region inside the wrapper of
.slds-context-bar needs the appropriate ordering class name, e.g.
1.1. Items on the Navigation Bar
Every item that sits on the horizontal axis of the navigation bar should receive the class
This class is used to notify the navigation bar that it has a new item. The styles applied allow the children of the navigation bar to vertically aligned, without knowing the height of the navigation bar. The styles will also allow for the actionable items
.slds-context-bar__icon-action to stretch 100% of the height of the navigation bar, optimizing the hit area of those actions.
Since the items are leveraging flexbox, the elements inside can easily be re-ordered easily by using an order class helper on the element, such as
1.2. Building the Navigation Bar Item
The navigation bar item is built to accommodate 2 specific layout needs.
- Individual text hyperlink to invokes link destination
- Individual text hyperlink to invokes link destination + button icon to indicate menu dropdown is available
These layouts are built upon 2 reusable classes. The text hyperlink action area would get the class
.slds-context-bar__label-action and the icon based action area would get the class
.slds-context-bar__icon-action class handles the alignment and coloring of the icons based on interactions such as
:active. This is a required if you have an actionable icon area adjacent to an actionable text area.
The markup structure should have the button icon(s) preceding the text label. The icons can be visually reordered by using the ordering utility classes such as
1.3. Building the Icons in the Navigation Bar
The icons in the navigation bar either serve as a visual affordance that indicates an item has a menu with additional actions or the icon itself is actionable.
The class used to indicate a button icon will sit adjacent to another actionable item is
.slds-context-bar__icon-action. If you two icons in an item, each icon should be contained in it’s own
The look and feel of the button icon is dependant on the modifiers used from Button Icon Variant Component page.
.slds-context-bar__icon-action styles apply a default left and right padding of 0.75rem. That padding can be removed or modified by using our spacing utilities. In example #1, the left padding has been removed by using the class
If a navigation bar item has an icon then we want to provide visual indication that its active when a user hovers into its region. To make this happen, apply the class
.slds-hint-parent to the hover region, most cases would be
1.4. Menu trigger area on Navigation Bar Items
When a navigation bar items requires a menu with additional sub options or actions, the classes that need to be added to the target hit area are the following:
.slds-context-bar__dropdown-trigger— Add a hoverable zone below the action so that the dropdown doesn’t disappear when the mouse is between the action and the dropdown — this is specific to the navigation bar
.slds-dropdown-trigger— Globally used utility that notifies the element there is a dropdown menu
.slds-dropdown-trigger_click— Specifies that an item requires a click to open interaction.
If the navigation item has one hyperlink with a menu containing additional sub actions, then the hover area that invokes the dropdown menu is both the
.slds-context-bar__icon-action. If the navigation item is demonstrated as a tab format, one hyperlink plus two additional actions, then the hover area that invokes the dropdown menu is only on the
1.5. Specifics of the Navigation Bar - App Launcher
1.6. Specifics of the Navigation Bar - App Name
The application name needs to receive the
.slds-context-bar__app-name class. This class will handle such things as its unique font sizing and truncation widths.
1.7. Specifics of the Navigation Bar - Divider
Due to the platform-esc nature of the navigation bar, there is an available element utility to apply a divider between sections where needed. The
.slds-context-bar__vertical-divider class should be applied to an empty
<div> and placed within the markup of your navigation bar for a visual divider.
Alternatively, two classes are available to add border using css. Adding the class
.slds-context-bar__item--divider-left will add a left border to a navigation bar item while
.slds-context-bar__item--divider-right will add a right border.
Overview of CSS Classes
- The CSS class being referred to.
- A description of what the class does.
- Whether the class name is dev-ready (meaning it's fully vetted and tested and safe to use) or prototype (which means it's not fully vetted yet).
- The selector that the class name is allowed to be used on.
- The base level pattern for a component. A variant can be extended to create another variant of that component, for example, a stateful button is a derivative of the base button.
- A single class that can be added to an HTML element of a component to modify its output. Typically these will be colors, sizing and positioning.